home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980424-19980901
/
000398_news@newsmaster….columbia.edu _Fri Aug 21 08:43:32 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id IAA18901
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 21 Aug 1998 08:43:31 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id IAA25377
for kermit.misc@watsun; Fri, 21 Aug 1998 08:43:31 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!jaltman
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Using server mode with K95 and TCP/IP network
Date: 21 Aug 1998 12:43:29 GMT
Organization: Columbia University
Lines: 47
Message-ID: <6rjq1h$h2l$1@apakabar.cc.columbia.edu>
References: <35DB7B52.FCC7A319@uq.net.au>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:9124
In article <35DB7B52.FCC7A319@uq.net.au>,
Rob Irvine <robi@hastdeer.com.au> wrote:
: I am trying to have a PC using K95 startup in server mode, and then
: allow a Unix system use Kermit to send it files in separate kermit
: sessions, and for the PC to stay in server mode continuously.
:
: I have disabled bye and finish on the server PC but get a screen of Ts
: at the end of the first Unix kermit session. Then I cannot start
: another Unix kermit session successfully and have to abort the K95 job.
:
: If I don't disable bye and/or finish I get the K95 server session
: stopping at the end of each Unix kermit session or at the end of the
: file send command.
:
: I have been successful in using this concept with a PC using Dos Kermit
: and a com1 port being in server mode to a Unix kermit session/s.
:
: Any advice would be appreciated.
It is one thing to lock a Kermit in SERVER mode when you have a
direct serial port connection that is not going to come and go.
However, this is a very bad idea when accepting incoming TCP/IP
connections. You do not provide a lot of information but I assume
you are attempting to perform the following:
SET NETWORK TYPE TCP/IP
WHILE TRUE {
SET HOST /SERVER * 6000
HANGUP
}
This answers an incoming connection on port 6000 and auto-starts
SERVER mode. When the connection drops, it waits for the next
call. This is necessary because each new connection is going to
be on a different incoming TCP/IP port. So the old port must be
closed.
There is a bug related to SET SERVER TIMEOUT and SET SERVER IDLE-TIMEOUT
in 1.1.17 that is producing the 'T's that you are seeing.
Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
The Kermit Project * Columbia University
612 West 115th St #716 * New York, NY * 10025
http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org